Skip to content

Conversation

@rgithubli
Copy link
Contributor

@rgithubli rgithubli commented Nov 11, 2025

Setting ergo flags using FLAG_SET_ERGO, instead of FLAG_SET_DEFAULT, so we can have the right origin info.

For ShenandoahEvacReserve change: when we use shenandoah passive mode and degen is also turned off (-XX:ShenandoahGCMode=passive -XX:-ShenandoahDegeneratedGC), we set the ShenandoahEvacReserve to 0:

if (!ShenandoahDegeneratedGC) {
SHENANDOAH_ERGO_OVERRIDE_DEFAULT(ShenandoahEvacReserve, 0);
}

FLAG_SET_DEFAULT doesn't check the range but FLAG_SET_ERGO does so some of the jtreg would fail because of this change. Had to move this ergo setting to regular FLAG_SET_DEFAULT.

Testing: jtreg gc. GHA pending.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed (2 reviews required, with at least 1 Reviewer, 1 Author)

Issue

  • JDK-8371381: [Shenandoah] Setting ergo flags should use FLAG_SET_ERGO (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28242/head:pull/28242
$ git checkout pull/28242

Update a local copy of the PR:
$ git checkout pull/28242
$ git pull https://git.openjdk.org/jdk.git pull/28242/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28242

View PR using the GUI difftool:
$ git pr show -t 28242

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28242.diff

Using Webrev

Link to Webrev Comment

@rgithubli rgithubli marked this pull request as ready for review November 11, 2025 18:24
@bridgekeeper
Copy link

bridgekeeper bot commented Nov 11, 2025

👋 Welcome back rgithubli! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Nov 11, 2025

@rgithubli This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8371381: [Shenandoah] Setting ergo flags should use FLAG_SET_ERGO

Reviewed-by: xpeng, wkemper, ysr, cslucas

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 82 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@ysramakrishna, @JohnTortugo, @pengxiaolong, @earthling-amzn) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added hotspot-gc hotspot-gc-dev@openjdk.org shenandoah shenandoah-dev@openjdk.org labels Nov 11, 2025
@openjdk
Copy link

openjdk bot commented Nov 11, 2025

@rgithubli The following labels will be automatically applied to this pull request:

  • hotspot-gc
  • shenandoah

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Nov 11, 2025
@mlbridge
Copy link

mlbridge bot commented Nov 11, 2025

Webrevs

Copy link
Member

@ysramakrishna ysramakrishna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the ergo flg setting macro changes. They look good to me.

For the passive mode that requires allowing evac reserve of 0, I'll request @kdnilsen or @earthling-amzn to review.

/reviewers 2

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Nov 11, 2025
@openjdk
Copy link

openjdk bot commented Nov 11, 2025

@ysramakrishna
The total number of required reviews for this PR (including the jcheck configuration and the last /reviewers command) is now set to 2 (with at least 1 Reviewer, 1 Author).

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Nov 11, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Nov 11, 2025
@earthling-amzn
Copy link
Contributor

Hmm, setting ShenandoahEvacReserve to zero will cause a divide by zero error in other modes (it will even cause a divide by zero error in the passive mode if ShenandoahDegeneratedGC is enabled). I'd rather contain the accommodation for this configuration to the passive mode, than accept values that will cause crashes. Could we "inline" the macro on line 41 and allow zero only for this special configuration (passive mode and only full gcs) by changing the "inlined" macro to use SET_DEFAULT still?

@@ -353,7 +353,7 @@
"evacuation collection set (comprised of both young and old " \
"regions) is also bounded by this parameter. In percents of " \
"total (young-generation) heap size.") \
range(1,100) \
range(0,100) \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we allow this, somebody will file a bug because -XX:ShenandoahEvacReserve=0 will cause other modes to crash with divide by zero error.

Copy link
Contributor Author

@rgithubli rgithubli Nov 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I'll keep the range as it is (1,100), but instead of setting the default with ergo at here:

if (!ShenandoahDegeneratedGC) {
SHENANDOAH_ERGO_OVERRIDE_DEFAULT(ShenandoahEvacReserve, 0);
}
I'll just use FLAG_SET_DEFAULT to bypass the check? We wouldn't have the data source origin in passive mode which is only meant to be diagnostic, but that's better than causing problems in the regular mode.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, missed your general comment above. I think we're talking about the same solution. I'll update the passive mode to use FLAG_SET_DEFAULT.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's what I was suggesting. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put the lower bound back to 1 now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, forgot. Updating.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Nov 12, 2025
@rgithubli
Copy link
Contributor Author

rgithubli commented Nov 12, 2025

GHA test test/jdk/java/util/Arrays/SortingNearlySortedPrimitive.java failed, but it uses g1, should be unrelated:

 # JRE version: OpenJDK Runtime Environment (26.0) (build 26-internal-rgithubli-6200456b7130997d227dd5a128e4cefbd05059b5)
# Java VM: OpenJDK 64-Bit Server VM (26-internal-rgithubli-6200456b7130997d227dd5a128e4cefbd05059b5, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x6765ff]  frame::sender(RegisterMap*) const+0x29f

It passed on my local. Rerun on GHA and check hs_err log.


Should be a non related compiler issue. Opened a JBS: https://bugs.openjdk.org/browse/JDK-8371747

Copy link
Contributor

@earthling-amzn earthling-amzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Nov 13, 2025
@rgithubli
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Nov 13, 2025
@openjdk
Copy link

openjdk bot commented Nov 13, 2025

@rgithubli
Your change (at version 6200456) is now ready to be sponsored by a Committer.

@pengxiaolong
Copy link

/sponsor

@openjdk
Copy link

openjdk bot commented Nov 13, 2025

Going to push as commit 2199b5f.
Since your change was applied there have been 82 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Nov 13, 2025
@openjdk openjdk bot closed this Nov 13, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Nov 13, 2025
@openjdk
Copy link

openjdk bot commented Nov 13, 2025

@pengxiaolong @rgithubli Pushed as commit 2199b5f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated shenandoah shenandoah-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

5 participants